Being software developers themselves, when the Selerix founders set out to perfect benefits enrollment technology they knew one of the biggest problems all engineers face is contingency planning.  No matter how hard we try and how much research we do, new requirements inevitably come along that add new clarity to the design model.  Introducing significant change to a system with a rigid architecture can threaten product integrity with complex refactoring that can result in defects, service downtime, or worse.  One measure of a good architecture, therefore, is a system's ability to cope with change.  At Selerix, the term scalable is more than just an industry standard buzzword; it is a fact.

To that end, one of the core design elements in the Selerix Benefits-Selection system architecture is the ability to override essentially any part of the enrollment with custom code.  While our goal is to provide simple click-and-go options that allow modifying default behavior, nothing beats a bit of brick and mortar when the time comes to add a new wing to the building.  Although most of the time customer-created script consists of only a few lines of code, internally the Selerix Product and Systems Integration teams use the same API that is available to our clients to build the BenSelect product and data extract library.

 

Contents

This section contains a reference to the OOP class properties, fields and methods Selerix exposes to developers to change system defaults and even integrate BenSelect enrollments into their own system.  The API is, for the most part, a collection of data accessor classes developers use to access, change and act on enrollment data on things such as:

• Group Info: general case setup information
• Forms: tools to modify existing and create new data used by various forms
• People: applicants, employees, dependents, agents, brokers, etc.
• Products: policy information such as name, payer, eligibility  and rates
• Reports: tools to modify existing and create new data for report output 
• Utilities: data validation and formatting,  object serialization, etc.

The reference includes interface prototypes for the most popular development languages using a hierarchical description model.  It defines the public methods, properties and fields for the various BenSelect elements that comprise our developer support library.

 

Selerix SDK Source

In addition to the reference documentation contained here, you may also want to take a look at the Selerix SDK example source, which contains a Visual Studio solution and a NetBeans Java project as a reference.  You can download the SDK here: https://dev.benefitagent.com/doc/sdk/sdk.zip.